feat(events): define v1 semantic route descriptors - #170

Separate event routes from input/result aliases

When a graph contains any newly admitted event route, this branch adds an EventRouteContract containing only component and event to AgentBundleRoutes, while the emitted RouteInput and RouteResult aliases at lines 47–48 still unconditionally index every RouteId by input and result. TypeScript therefore reports TS2536 while checking the generated routes.d.ts, preventing consumers from type-checking generated declarations for projects with event routes. Restrict those aliases to schema-based route IDs or extract the properties conditionally.

Useful? React with 👍 / 👎.

Fixed in #198 (merged as d992838). The generated declarations now route RouteInput/RouteResult through conditional ContractInput/ContractResult helpers: schema routes keep their schema-derived types, and event routes resolve the component's props and awaited return type instead of erroring on the missing input/result members. Covered by a typegen fixture test plus a type-level test that compiles the generated routes.d.ts and asserts exact resolution for both route kinds.

Pass the published event props from the route test harness

Consumers authoring against this new public contract cannot exercise their event routes through agent-bundle/test: componentProps in src/test/render.ts still passes { event, payload, signal } for event-route, rather than { canonical, native, signal }, and its event value is the prefixed route ID such as event:tool/after. Consequently, routes that destructure the newly documented canonical or native props receive undefined and may fail during route-unit rendering; the harness needs to construct the same canonical/native envelope promised here.

Useful? React with 👍 / 👎.